Temporary pipeline marking for processor error workarounds

ABSTRACT

Embodiments include a computer system for temporary pipeline marking for processor error workarounds, the computer system having a processor configured to perform a method. The method includes monitoring a pipeline of the processor for an event that is predetermined to place the processor in a stuck state that results in an errant instruction execution result due to the stuck state or repeated resource contention causing performance degradation. The pipeline is marked for a workaround action based on detecting the event. A clearing action is triggered based on the marking of the pipeline. The marking of the pipeline is cleared based on the triggering of the clearing action.

PRIORITY

This application is a Continuation of legally related U.S. applicationSer. No. 15/074,219 filed Mar. 18, 2016, which is a Continuation of U.S.patent application Ser. No. 14/641,553, filed on Mar. 9, 2015, theentire contents of which are incorporated herein by reference.

BACKGROUND

The present application relates generally to an improved data processingsystem and method. More specifically, the present application isdirected to a system and method for temporary pipeline marking forprocessor error workarounds.

In modern processor design, especially in an out-of-order processordesign, design flaws in a pipeline can result in control stateinformation living beyond the instruction for which it is intended,resulting in incorrect processing of the next instruction in thatpipeline. Hung state information (as this form of design error refersto) is one of the most difficult problems to find and solve during adesign phase, and are often not found until later when the design isimplemented in hardware.

As another example, one or more state values used by a state machinethat manages a pipeline in a processor can have a hung or stuck statevalue if the pipeline is at least partially cleared by a pipeline flushor an instruction rescind. In the processor, conditions can occur whichrequire instructions currently executing in execution unit hardware ofthe processor to be flushed. For example, branches, load operations thatmiss the cache, exceptions, and the like can result in a pipeline flush.When instructions are flushed, state machines and control sequencers mayneed to be reset for the next operation to be executed successfully.

Failure to properly flush state from the control hardware of anexecution unit is a source of design errors in processor designs,particularly for cases where complex instructions iteratively run formany cycles in the execution hardware (divide operations, for example).If a design error that results in an incomplete state reset for aparticular instruction or instruction type is caught early in the designprocess, the design can be fixed without substantial penalty. However,if the design error is not detected until late in the design process,developing a workaround can be difficult.

SUMMARY

Embodiments include a method for temporary pipeline marking forprocessor error workarounds. The method includes monitoring a pipelineof a processor for an event that is predetermined to place the processorin a stuck state that results in an errant instruction execution resultdue to the stuck state or repeated resource contention causingperformance degradation. The pipeline is marked for a workaround actionbased on detecting the event. A clearing action is triggered based onthe marking of the pipeline. The marking of the pipeline is clearedbased on the triggering of the clearing action.

Embodiments include a computer system for temporary pipeline marking forprocessor error workarounds, the computer system having a processorconfigured to perform a method. The method includes monitoring apipeline of the processor for an event that is predetermined to placethe processor in a stuck state that results in an errant instructionexecution result due to the stuck state or repeated resource contentioncausing performance degradation. The pipeline is marked for a workaroundaction based on detecting the event. A clearing action is triggeredbased on the marking of the pipeline. The marking of the pipeline iscleared based on the triggering of the clearing action.

Embodiments also include a computer program product for temporarypipeline marking for processor error workarounds, the computer programproduct including a computer readable storage medium having computerreadable program code embodied therewith. The computer readable programcode including computer readable program code is configured to perform amethod. The method includes monitoring a pipeline of a processor for anevent that is predetermined to place the processor in a stuck state thatresults in an errant instruction execution result due to the stuck stateor repeated resource contention causing performance degradation. Thepipeline is marked for a workaround action based on detecting the event.A clearing action is triggered based on the marking of the pipeline. Themarking of the pipeline is cleared based on the triggering of theclearing action.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 is an exemplary diagram of a distributed data processing systemin which aspects of the exemplary embodiments may be implemented;

FIG. 2 is an exemplary block diagram of a data processing device inwhich aspects of the exemplary embodiments may be implemented;

FIG. 3 is an exemplary diagram illustrating a pipeline of a processor inaccordance with one exemplary embodiment;

FIG. 4 illustrates a diagram of an execution unit pipeline withtemporary pipeline marking in accordance with one embodiment;

FIG. 5 illustrates a diagram of a load store unit pipeline withtemporary pipeline marking in accordance with another embodiment; and

FIG. 6 illustrates a flow diagram of a method for temporary pipelinemarking for processor error workarounds in accordance with anembodiment.

DETAILED DESCRIPTION

Exemplary embodiments include systems, methods and computer programproducts for temporary pipeline marking for processor error workarounds.During execution, a processor may contain latches that contain a stuckstate in which an error may result from subsequent instruction executionbased on the stuck state. Embodiments provide a workaround mechanismthat allows test engineers to program conditions in hardware known tohave design flaws when an event occurs that results in a latchcontaining stuck state information which will result in a subsequenterror. Temporary pipeline marking may be implemented by a programmablecondition engine that keeps track of possible stuck states in a pipelineand marks the pipeline for a workaround action based on detecting theevent. For example, in an execution unit pipeline, a next instruction inthe execution unit pipeline having a same instruction type as aprogrammable instruction operational code can be marked to initiate astuck state clearing action upon instruction completion. A stuck stateclearing action can be a complete purging of the pipeline, for example,by use of an XCOND. An XCOND is an immediate reset condition thatcancels all current execution, clears latches, and restores theprocessor to the last completed, checked, and saved state. As anotherexample, the stuck state clearing action may be a subsequent pipelineflush event based on the next instruction having the same instructiontype reaching a same pipeline stage that results in the stuck stateprior to completion of the next instruction, where the next instructionclears the stuck state by passing through the pipeline stage associatedwith the stuck state.

The exemplary embodiments may be implemented in any processor of anycomputing device. For example, the exemplary embodiments may be used inany of a server computing device, client computing device, communicationdevice, portable computing device, or the like. FIGS. 1-2 are providedhereafter as examples of a distributed data processing environment andcomputing devices in which exemplary aspects of the illustrativeembodiments may be implemented. FIGS. 1-2 are only exemplary and are notintended to state or imply any limitation with regard to the types ofcomputing devices in which the illustrative embodiments may beimplemented. To the contrary, the exemplary embodiments may beimplemented in any processor regardless of the particular machine orcomputing device in which the processor is ultimately operating.

With reference now to the figures, FIG. 1 depicts a pictorialrepresentation of an exemplary distributed data processing system inwhich aspects of the illustrative embodiments may be implemented.Distributed data processing system 100 may include a network ofcomputers in which embodiments of the illustrative embodiments may beimplemented. The distributed data processing system 100 contains atleast one network 102, which is the medium used to provide communicationlinks between various devices and computers connected together withindistributed data processing system 100. The network 102 may includeconnections, such as wire, wireless communication links, or fiber opticcables.

In the depicted example, server 104 and server 106 are connected tonetwork 102 along with storage unit 108. In addition, clients 110, 112,and 114 are also connected to network 102. These clients 110, 112, and114 may be, for example, personal computers, network computers, or thelike. In the depicted example, server 104 provides data, such as bootfiles, operating system images, and applications to the clients 110,112, and 114. Clients 110, 112, and 114 are clients to server 104 in thedepicted example. Distributed data processing system 100 may includeadditional servers, clients, and other devices not shown.

In the depicted example, distributed data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, the distributed data processing system 100 may also beimplemented to include a number of different types of networks, such asfor example, an intranet, a local area network (LAN), a wide areanetwork (WAN), or the like. As stated above, FIG. 1 is intended as anexample, not as an architectural limitation for different embodiments ofthe present invention, and therefore, the particular elements shown inFIG. 1 should not be considered limiting with regard to the environmentsin which the exemplary embodiments of the present invention may beimplemented.

With reference now to FIG. 2, a block diagram of an exemplary dataprocessing system is shown in which aspects of the exemplary embodimentsmay be implemented. Data processing system 200 is an example of acomputer, such as server 104 or client 110 in FIG. 1, in which computerusable code or instructions implementing the processes for exemplaryembodiments of the present invention may be located.

In the depicted example, data processing system 200 employs a hubarchitecture including a north bridge and memory controller hub (NB/MCH)202 and a south bridge and input/output (I/O) controller hub (SB/ICH)204. Processing unit 206, main memory 208, and graphics processor 210are connected to NB/MCH 202. Graphics processor 210 may be connected toNB/MCH 202 through an accelerated graphics port (AGP).

In the depicted example, local area network (LAN) adapter 212 connectsto SB/ICH 204. Audio adapter 216, keyboard and mouse adapter 220, modem222, read only memory (ROM) 224, hard disk drive (HDD) 226, CD-ROM drive230, universal serial bus (USB) ports and other communication ports 232,and PCI/PCIe devices 234 connect to SB/ICH 204 through bus 238 and bus240. PCI/PCIe devices may include, for example, Ethernet adapters,add-in cards, and PC cards for notebook computers. PCI uses a card buscontroller, while PCIe does not. ROM 224 may be, for example, a flashbinary input/output system (BIOS).

HDD 226 and CD-ROM drive 230 connect to SB/ICH 204 through bus 240. HDD226 and CD-ROM drive 230 may use, for example, an integrated driveelectronics (IDE) or serial advanced technology attachment (SATA)interface. Super I/O (SIO) device 236 may be connected to SB/ICH 204.

An operating system runs on processing unit 206. The operating systemcoordinates and provides control of various components within the dataprocessing system 200 in FIG. 2. As a client, the operating system maybe a commercially available operating system. An object-orientedprogramming system, such as the Java™ programming system, may run inconjunction with the operating system and provides calls to theoperating system from Java™ programs or applications executing on dataprocessing system 200 (Java is a trademark of Sun Microsystems, Inc. inthe United States, other countries, or both).

As a server, data processing system 200 may be, for example, an IBMSystem p, an IBM System z, or other computer system. Data processingsystem 200 may be a symmetric multiprocessor (SMP) system including aplurality of processors in processing unit 206. Alternatively, a singleprocessor system may be employed.

Instructions for the operating system, the object-oriented programmingsystem, and applications or programs are located on storage devices,such as HDD 226, and may be loaded into main memory 208 for execution byprocessing unit 206. The processes for exemplary embodiments of thepresent invention may be performed by processing unit 206 using computerusable program code, which may be located in a memory such as, forexample, main memory 208, ROM 224, or in one or more peripheral devices226 and 230, for example.

A bus system, such as bus 238 or bus 240 as shown in FIG. 2, may becomprised of one or more buses. Of course, the bus system may beimplemented using any type of communication fabric or architecture thatprovides for a transfer of data between different components or devicesattached to the fabric or architecture. A communication unit, such asmodem 222 or network adapter 212 of FIG. 2, may include one or moredevices used to transmit and receive data. A memory may be, for example,main memory 208, ROM 224, or a cache such as found in NB/MCH 202 in FIG.2.

Those of ordinary skill in the art will appreciate that the hardware inFIGS. 1-2 may vary depending on the implementation. Other internalhardware or peripheral devices, such as flash memory, equivalentnon-volatile memory, or optical disk drives and the like, may be used inaddition to or in place of the hardware depicted in FIGS. 1-2. Also, theprocesses of the exemplary embodiments may be applied to amultiprocessor data processing system, other than the SMP systemmentioned previously, without departing from the spirit and scope of thepresent invention.

Moreover, the data processing system 200 may take the form of any of anumber of different data processing systems including client computingdevices, server computing devices, a tablet computer, laptop computer,telephone or other communication device, a personal digital assistant(PDA), or the like. In some examples, data processing system 200 may bea portable computing device which is configured with flash memory toprovide non-volatile memory for storing operating system files and/oruser-generated data, for example. Essentially, data processing system200 may be any known or later developed data processing system withoutarchitectural limitation.

FIG. 3 is an exemplary diagram illustrating a pipeline of a processor300 in accordance with an embodiment. As shown in FIG. 3, the processor300 includes a processor pipeline comprised of a fetch addressmultiplexer 304, a fetch unit 310, decode unit 320, issue unit 330,execution unit 340, completion unit 350, and branch unit 360. The fetchunit 310, decode unit 320, issue unit 330, execution unit 340,completion unit 350, and/or other units of the processor 300 notdepicted in FIG. 3 may each have one or more pipelines with multiplestages. The processor 300 is coupled to memory subsystem 370, host bus380, bus control unit 390, main memory unit 392, and other processor andexternal devices 394, such as those depicted in FIG. 2, for example. Thefetch address multiplexer 304 selects an address from which the fetchunit 310 fetches instructions, such as reset address 302, programcounter address 321, branch address 322, flush address 323, or interruptaddress 324. The flush address 323 can be used to retry a set ofinstructions by reverting to an earlier point in an instruction stream.After instruction decoding by the decode unit 320, the issue unit 330can route and sequence instructions to the execution unit 340,completion unit 350, and branch unit 360.

A stuck state value may exist within a pipeline of the fetch unit 310,decode unit 320, issue unit 330, execution unit 304, completion unit350, and/or other units of the processor 300 not depicted in FIG. 3. Thestuck state value can lead to errant results upon subsequent use of thepipeline in which the stuck state value resides. Embodiments provide anerror workaround to clear stuck state values in one or more pipelines ofthe processor 300 using temporary pipeline marking.

Referring now to FIG. 4, a diagram 400 of an execution unit pipeline 402with temporary pipeline marking in accordance with an embodiment isshown. The example of FIG. 4 depicts stages 404 of instruction executionas blocks of an 8-cycle deep pipeline, where instructions enter the topon instruction issue and finish out the bottom to finish logic 406. Thefinish logic 406 may be part of issue unit 330 or completion unit 350 ofFIG. 3, where the execution unit pipeline 402 is part of execution unit340 of FIG. 3. A pipeline controller 408 can receive an instructionissue 410 from the issue unit 330 and route it to the correspondingexecution unit pipeline, such as the execution unit pipeline 402. Itwill be understood that multiple instances of the execution unitpipeline 402 can be implemented in the processor 300 of FIG. 3, such asdifferent units for fixed-point and floating-point operations. Thepipeline controller 408 can also receive events and information 412 thatmay include control signals, information, and conditions that may beassociated with cancelling or flushing an instruction or instructionsthat are partially executed in pipeline stages 404. Examples include apipeline flush event and/or a rescind event. A pipeline flush event maytarget a particular stage 404 or may clear out one more stages 404 andmay require additional clearing of stages 404 for multiple cycles goingforward, while a rescind event may clear only a single targeted stage404 for a targeted instruction. To clear one or more stages 404, thepipeline controller 408 can track instruction execution and send outflush and kill indicators 414 to identify which stages 404 include aninstruction or instructions that must be removed. A multi-cycleinstruction may exist in several and possibly all of the stages 404 ofthe execution unit pipeline 402, depending on the length of executionand how far instruction execution has progressed when a kill requestarrives. Temporary pipeline marking may be applied to execution unitpipeline 402 when one of these flush or rescind events occur if a designerror has been found to exist that causes a latch on that pipeline tohave incorrectly held state under these circumstances so the nextinstruction executed on that pipeline can finish with an XCOND.

In exemplary embodiments, a programmable condition engine 416 monitorsissued instructions 418 that are sent to the execution unit pipeline 402from the pipeline controller 408. The programmable condition engine 416also receives one or more flush and kill indicators 414. Programminginformation 420 in the programmable condition engine 416 is set up tomonitor for any one of a broad set of conditions specific to a problemarea as an event that is predetermined to cause incorrect state to beheld in a latch (stuck state) in execution pipeline 403. For example, ifa stuck state is found upon killing a specific instruction, but thestuck state only occurs when the result is close to a predeterminedlimit, the programming information 420 can be set to only look for akilled instruction of the same type with results near the predeterminedlimit. One of more programmable instruction operational codes can bestored in the programming information 420 to identify the specificinstruction or instruction type that triggers an action. The flexibleset of programming information 420 allows pipeline marking to be invokedon either a very wide range of conditions or on a very specific set ofconditions.

By limiting actions to target specific cases, performance impacts of thestuck state clearing action can be significantly limited, as onlyspecific cases that are known to have problems will have to incur anextended period resetting action with an XCOND to completely purge theexecution unit pipeline 402 and associated internal states.

Once a condition is identified on a killed/flushed instruction, stateinformation 422 is set in the programmable condition engine 416. Thestate information 422 is used to inject an action 424 (i.e., aworkaround action that temporarily marks the pipeline) onto the nextinstruction that executes on that execution unit pipeline 402. Oneexample of the action 424 is an XCOND that triggers a reset (i.e., astuck state clearing action on all latches) of the execution unitpipeline 402 as a complete purge and guarantees any state information inthe execution unit 340 of FIG. 3 that potentially got stuck when theinstruction was killed will be cleared. The programmable conditionengine 416 may inject the XCOND as the action 424 on the instructionfollowing the killed instruction, and it can also be verified that theinstruction that includes the XCOND (i.e., a marked instruction) as theinjected action 424 actually finishes by finishing with a conditionalaction 426 at finish logic 406. If the marked instruction does notfinish, no XCOND will occur for the execution unit 340 of FIG. 3. Ifthis happens, another instruction in the execution unit pipeline 402 canalso be marked with XCOND as the inject action 424.

Groups of instructions that progress down a branch wrong path tend to beflushed together. Therefore, instructions on the execution unit pipeline402 may continue to be marked with an XCOND as the action 424 until aninstruction finally finishes with the conditional action 426 applied sothe execution unit pipeline 402 can be reset.

In an alternate embodiment, instructions are not marked with an XCOND asthe action 424 if the first instruction marked with as XCOND does notfinish. For example, if a multi-cycle instruction is flushed, and a nextinstruction down the execution unit pipeline 402 is marked with an XCONDbut also flushes, a third instruction is not marked with an XCOND. AnXCOND may not be necessary to clear a stuck state, but simply sendinganother instruction down the execution unit pipeline 402 can clean upthe execution unit pipeline 402. The next instruction having a sameinstruction type may gather and clear any stuck state as it passes downthe execution unit pipeline 402. However, the instruction that clearsthe stuck state may be corrupted with the stuck state as it is gathered,resulting in a wrong result. If the instruction is also flushed, thereis no need to perform an XCOND on the execution unit pipeline 402 as thestuck state is flushed away with the instruction that gathered it. Thus,the conditional action 426 may not be needed for a marked instructionwhere a previous instruction cleared the stuck state by passing througha stage 404 that is associated with the stuck state, where that previousinstruction was flushed before reaching finish logic 406.

FIG. 5 illustrates a diagram 500 of a load store unit pipeline 502 withtemporary pipeline marking in accordance with an embodiment is shown.The load store unit pipeline 502 may be part of a load store unitcoupled to the decode unit 320 and execution unit 340 of FIG. 3. Theload store unit pipeline 502 includes a plurality of stages 504. Finishlogic 506 may be allocated to the issue unit 330, the execution unit340, and/or the completion unit 350 of FIG. 3. In the example of FIG. 5,a load store operation is issued 510 to a pipeline controller 508. Loadstore operations can access memory subsystem 370 of FIG. 3, as well asinternal registers and caches (not depicted). Events and information 512may be associated with a particular memory address. A programmablecondition engine 516 can monitor for repeated resource contention withrespect to a shared resource and trigger a workaround action as aninject action 524 upon confirming that the event has occurred for apredetermined number of times. For instance, programming information 520can identify a contention address and a number of times to confirm.State information 522 may indicate a current state as issued load storeoperations 518 move through the stages 504 of the load store unitpipeline 502. Upon a finish with conditional action 526 reaching finishlogic 506, the contention can be broken by forcing a complete purging ofthe load store unit pipeline 502 to stagger timing of attempted accessesto a shared resource. For instance, if the load store unit pipeline 502performs an XCOND every third access conflict of a shared memorylocation, the timing of repeated resource contention is disturbed suchthat a resource contention condition is removed.

Referring now to FIG. 6, a flow chart diagram of a method 600 fortemporary pipeline marking for processor error workarounds in aprocessor pipeline to prevent erroneous calculation or performancedegradation due to repeated resource contention in accordance with anexemplary embodiment is shown. As shown at block 602, the method 600includes monitoring a pipeline of a processor, such as processor 300 ofFIG. 3, for an event that is predetermined to place the processor in astuck state that results in an errant instruction execution result dueto the stuck state or repeated resource contention. The pipeline may bethe execution unit pipeline 402 of FIG. 4, and the event can be apipeline flush event or a rescind event. The event may be associatedwith a programmable instruction operational code in programmablecondition engine 416 of FIG. 4. The repeated resource contention may bewith respect to a shared resource, and triggering a clearing action mayinclude confirming that the event has occurred for a predeterminednumber of times, where the pipeline is the load store unit pipeline 502of FIG. 5 and the event is associated with a memory address.

At block 604, the pipeline is marked for a workaround action based ondetecting the event. Marking can be performed by injecting an actioninto the pipeline, such as adding an XCOND action to be executed uponfinishing an instruction. At block 606, a clearing action is triggeredbased on the marking of the pipeline. The clearing action can clear astuck state in one or more latches. The triggering of the clearingaction may be conditionally triggered by a next instruction in theexecution unit pipeline 402 of FIG. 4 having a same instruction type asthe programmable instruction operational code. Finish logic in theprocessor can initiate the clearing action based on the marking and thenext instruction having the same instruction type reaching the finishlogic. The clearing action may be a subsequent pipeline flush eventbased on the next instruction having the same instruction type reachinga same pipeline stage that results in a stuck state prior to completionof the next instruction. At block 608, the marking of the pipeline iscleared based on the triggering of the clearing action. The clearingaction may include a complete purging of the pipeline.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

This disclosure has been presented for purposes of illustration anddescription but is not intended to be exhaustive or limiting. Manymodifications and variations will be apparent to those of ordinary skillin the art. The embodiments were chosen and described in order toexplain principles and practical application, and to enable others ofordinary skill in the art to understand the disclosure.

Although illustrative embodiments of the invention have been describedherein with reference to the accompanying drawings, it is to beunderstood that the embodiments of the invention are not limited tothose precise embodiments, and that various other changes andmodifications may be affected therein by one skilled in the art withoutdeparting from the scope or spirit of the disclosure.

What is claimed is:
 1. A computer system for temporary pipeline markingfor processor error workarounds, the computer system comprising: aprocessor comprising an execution unit pipeline, the processorconfigured to perform: monitoring the execution unit pipeline for anevent that is predetermined to cause a stuck state that results in anerrant instruction execution result due to the stuck state, wherein theevent comprises a pipeline flush event or a rescind event, and the eventis associated with a programmable instruction operational code; markingthe execution unit pipeline for a workaround action based on detectingthe event; triggering a clearing action based on the marking of theexecution unit pipeline, wherein the triggering is conditionallytriggered by a next instruction in the execution unit pipeline having asame instruction type as the programmable instruction operational code,the clearing action comprises a complete purging of the execution unitpipeline; and clearing the marking of the execution unit pipeline basedon the triggering of the clearing action, wherein finish logic in theprocessor initiates the clearing action based on the marking and thenext instruction having the same instruction type reaching the finishlogic and marks another instruction in the execution unit pipeline totrigger the clearing action based on determining that the nextinstruction having the same instruction type did not finish at thefinishing logic.